Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: philippotto
PR: #8602
File: frontend/javascripts/oxalis/model/volumetracing/volume_annotation_sampling.ts:365-366
Timestamp: 2025-05-07T06:17:32.810Z
Learning: The parameter in applyVoxelMap was renamed from sliceCount to sliceOffset to better reflect its purpose, but this doesn't affect existing call sites since JavaScript/TypeScript function calls are position-based.

Learnt from: MichaelBuessemeyer
PR: #8485
File: frontend/javascripts/oxalis/model/accessors/dataset_layer_transformation_accessor.ts:384-392
Timestamp: 2025-04-01T09:45:17.527Z
Learning: The function isRotationAndMirrorMaybeOnly in the dataset_layer_transformation_accessor.ts is intentionally designed to allow mirroring transformations (negative scale values). It uses the length comparison (scale.length() === NON_SCALED_VECTOR.length()) rather than component equality to permit mirrored axes while ensuring the overall scale magnitude remains the same.

Learnt from: frcroth
PR: #8202
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/DatasetErrorLoggingService.scala:68-72
Timestamp: 2024-11-25T10:02:03.702Z
Learning: In DatasetErrorLoggingService.scala, prefer using TextUtils.stackTraceAsString(exception) when logging exceptions instead of passing the exception directly to logger.error.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: philippotto
PR: #8542
File: frontend/javascripts/viewer/model/sagas/volumetracing_saga.tsx:0-0
Timestamp: 2025-05-30T12:36:09.930Z
Learning: The WebKnossos frontend follows Redux immutability principles where reducers act immutably and create new state objects when changes occur. This makes reference equality checks (like prevVolumeTracing.segments !== volumeTracing.segments) reliable and efficient for detecting actual state changes, allowing memoization to work correctly.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: philippotto
PR: #8602
File: frontend/javascripts/oxalis/model/volumetracing/volume_annotation_sampling.ts:365-366
Timestamp: 2025-05-07T06:17:32.810Z
Learning: The parameter in applyVoxelMap was renamed from sliceCount to sliceOffset to better reflect its purpose, but this doesn't affect existing call sites since JavaScript/TypeScript function calls are position-based.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/NeuroglancerMeshHelper.scala:143-152
Timestamp: 2025-04-30T08:54:11.252Z
Learning: In Neuroglancer's sharded format, mesh fragment data is located immediately before the manifest file in the same shard data file. The correct way to calculate the mesh data starting offset is to subtract the total mesh size from the manifest starting offset (neuroglancerOffsetStart - totalMeshSize), not by adding the manifest size.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/volumetracing_saga.tsx:433-434
Timestamp: 2024-11-22T17:19:07.947Z
Learning: In the codebase, certain usages of segmentationLayer.resolutions are intentionally retained and should not be changed to segmentationLayer.mags during refactoring.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/NeuroglancerPrecomputedMeshFileService.scala:161-166
Timestamp: 2025-04-28T14:18:04.368Z
Learning: In Scala for-comprehensions with the Fox error handling monad, Fox.fromBool() expressions should use the <- binding operator instead of the = assignment operator to properly propagate error conditions. Using = will cause validation failures to be silently ignored.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8202
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/DatasetErrorLoggingService.scala:68-72
Timestamp: 2024-11-25T10:02:03.702Z
Learning: In DatasetErrorLoggingService.scala, prefer using TextUtils.stackTraceAsString(exception) when logging exceptions instead of passing the exception directly to logger.error.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/volumetracing_saga.tsx:433-434
Timestamp: 2024-11-22T17:19:07.947Z
Learning: In the codebase, certain usages of segmentationLayer.resolutions are intentionally retained and should not be changed to segmentationLayer.mags during refactoring.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: MichaelBuessemeyer
PR: #8221
File: CHANGELOG.unreleased.md:14-14
Timestamp: 2024-11-25T14:52:23.201Z
Learning: For the webknossos project, changelog entries in CHANGELOG.unreleased.md should be concise and avoid unnecessary detailed explanations.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/reducers/skeletontracing_reducer_helpers.ts:125-125
Timestamp: 2024-11-22T17:17:39.914Z
Learning: In the createNode function within skeletontracing_reducer_helpers.ts, the property resolution is intentionally kept even when the parameter is renamed to mag.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: frcroth
PR: #8598
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/models/datasource/DatasetLayerAttachments.scala:89-95
Timestamp: 2025-06-02T09:49:51.047Z
Learning: In WebKnossos dataset layer attachments, multiple file types can safely use the same directory name (like "agglomerates") because the scanning logic filters by file extension. For example, AgglomerateFileInfo scans for .hdf5 files while CumsumFileInfo scans for .json files in the same "agglomerates" directory without interference.

Learnt from: philippotto
PR: #8602
File: frontend/javascripts/oxalis/model/volumetracing/volume_annotation_sampling.ts:365-366
Timestamp: 2025-05-07T06:17:32.810Z
Learning: The parameter in applyVoxelMap was renamed from sliceCount to sliceOffset to better reflect its purpose, but this doesn't affect existing call sites since JavaScript/TypeScript function calls are position-based.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: MichaelBuessemeyer
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/datareaders/precomputed/NeuroglancerPrecomputedShardingUtils.scala:23-28
Timestamp: 2025-04-25T11:06:13.275Z
Learning: AlfuCache in the WebKnossos codebase has default configured TTL (time-to-live) and size limits, providing automatic protection against unbounded memory growth.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/reducers/skeletontracing_reducer_helpers.ts:125-125
Timestamp: 2024-11-22T17:17:39.914Z
Learning: In the createNode function within skeletontracing_reducer_helpers.ts, the property resolution is intentionally kept even when the parameter is renamed to mag.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/volumetracing_saga.tsx:433-434
Timestamp: 2024-11-22T17:19:07.947Z
Learning: In the codebase, certain usages of segmentationLayer.resolutions are intentionally retained and should not be changed to segmentationLayer.mags during refactoring.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/NeuroglancerPrecomputedMeshFileService.scala:161-166
Timestamp: 2025-04-28T14:18:04.368Z
Learning: In Scala for-comprehensions with the Fox error handling monad, Fox.fromBool() expressions should use the <- binding operator instead of the = assignment operator to properly propagate error conditions. Using = will cause validation failures to be silently ignored.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: MichaelBuessemeyer
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/datareaders/precomputed/NeuroglancerPrecomputedShardingUtils.scala:23-28
Timestamp: 2025-04-25T11:06:13.275Z
Learning: AlfuCache in the WebKnossos codebase has default configured TTL (time-to-live) and size limits, providing automatic protection against unbounded memory growth.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/volumetracing_saga.tsx:433-434
Timestamp: 2024-11-22T17:19:07.947Z
Learning: In the codebase, certain usages of segmentationLayer.resolutions are intentionally retained and should not be changed to segmentationLayer.mags during refactoring.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/reducers/skeletontracing_reducer_helpers.ts:125-125
Timestamp: 2024-11-22T17:17:39.914Z
Learning: In the createNode function within skeletontracing_reducer_helpers.ts, the property resolution is intentionally kept even when the parameter is renamed to mag.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: MichaelBuessemeyer
PR: #8325
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/image/ImageCreator.scala:0-0
Timestamp: 2025-02-24T08:22:51.814Z
Learning: In ImageCreator.scala, precision loss during uint64 to double conversion is acceptable because the values are only used for image generation where each color component is ultimately represented as a single byte in ARGB format. For grayscale values (except uint24 which represents RGB), each color only uses 8 bits anyway.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8598
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/models/datasource/DatasetLayerAttachments.scala:89-95
Timestamp: 2025-06-02T09:49:51.047Z
Learning: In WebKnossos dataset layer attachments, multiple file types can safely use the same directory name (like "agglomerates") because the scanning logic filters by file extension. For example, AgglomerateFileInfo scans for .hdf5 files while CumsumFileInfo scans for .json files in the same "agglomerates" directory without interference.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8202
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/DatasetErrorLoggingService.scala:68-72
Timestamp: 2024-11-25T10:02:03.702Z
Learning: In DatasetErrorLoggingService.scala, prefer using TextUtils.stackTraceAsString(exception) when logging exceptions instead of passing the exception directly to logger.error.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

webknossos-datastore/app/com/scalableminds/webknossos/datastore/controllers/DataSourceController.scala (1)

• invalidateCache (685-690)

app/models/job/Job.scala (1)

• datasetId (55-55)

frontend/javascripts/admin/rest_api.ts (1)

• deleteDatasetOnDisk (1347-1357)

frontend/javascripts/admin/rest_api.ts (1)

• createDatasetComposition (1104-1122)

frontend/javascripts/types/api_types.ts (1)

• APIDataset (242-245)

frontend/javascripts/admin/rest_api.ts (1)

• updateDatasetDatasource (984-995)

app/models/dataset/WKRemoteDataStoreClient.scala (1)

• hasSegmentIndexFile (80-90)

util/src/main/scala/com/scalableminds/util/objectid/ObjectId.scala (1)

• toString (12-12)

[style] ~104-~104: For conciseness, consider replacing this expression with an adverb.
Context: ...ynonymously for mags throughout the UI. At the moment, WebKnossos guarantees correct renderin...

(AT_THE_MOMENT)

125-125: Unordered list style
Expected: dash; Actual: plus

(MD004, ul-style)

126-126: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

127-127: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: philippotto
PR: #8602
File: frontend/javascripts/oxalis/model/volumetracing/volume_annotation_sampling.ts:365-366
Timestamp: 2025-05-07T06:17:32.810Z
Learning: The parameter in applyVoxelMap was renamed from sliceCount to sliceOffset to better reflect its purpose, but this doesn't affect existing call sites since JavaScript/TypeScript function calls are position-based.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: philippotto
PR: #8602
File: frontend/javascripts/oxalis/model/volumetracing/volume_annotation_sampling.ts:365-366
Timestamp: 2025-05-07T06:17:32.810Z
Learning: The parameter in applyVoxelMap was renamed from sliceCount to sliceOffset to better reflect its purpose, but this doesn't affect existing call sites since JavaScript/TypeScript function calls are position-based.

Learnt from: MichaelBuessemeyer
PR: #8485
File: frontend/javascripts/oxalis/model/accessors/dataset_layer_transformation_accessor.ts:384-392
Timestamp: 2025-04-01T09:45:17.527Z
Learning: The function isRotationAndMirrorMaybeOnly in the dataset_layer_transformation_accessor.ts is intentionally designed to allow mirroring transformations (negative scale values). It uses the length comparison (scale.length() === NON_SCALED_VECTOR.length()) rather than component equality to permit mirrored axes while ensuring the overall scale magnitude remains the same.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8202
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/DatasetErrorLoggingService.scala:68-72
Timestamp: 2024-11-25T10:02:03.702Z
Learning: In DatasetErrorLoggingService.scala, prefer using TextUtils.stackTraceAsString(exception) when logging exceptions instead of passing the exception directly to logger.error.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: philippotto
PR: #8602
File: frontend/javascripts/oxalis/model/volumetracing/volume_annotation_sampling.ts:365-366
Timestamp: 2025-05-07T06:17:32.810Z
Learning: The parameter in applyVoxelMap was renamed from sliceCount to sliceOffset to better reflect its purpose, but this doesn't affect existing call sites since JavaScript/TypeScript function calls are position-based.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/NeuroglancerMeshHelper.scala:143-152
Timestamp: 2025-04-30T08:54:11.252Z
Learning: In Neuroglancer's sharded format, mesh fragment data is located immediately before the manifest file in the same shard data file. The correct way to calculate the mesh data starting offset is to subtract the total mesh size from the manifest starting offset (neuroglancerOffsetStart - totalMeshSize), not by adding the manifest size.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: philippotto
PR: #8602
File: frontend/javascripts/oxalis/model/volumetracing/volume_annotation_sampling.ts:365-366
Timestamp: 2025-05-07T06:17:32.810Z
Learning: The parameter in applyVoxelMap was renamed from sliceCount to sliceOffset to better reflect its purpose, but this doesn't affect existing call sites since JavaScript/TypeScript function calls are position-based.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/volumetracing_saga.tsx:433-434
Timestamp: 2024-11-22T17:19:07.947Z
Learning: In the codebase, certain usages of segmentationLayer.resolutions are intentionally retained and should not be changed to segmentationLayer.mags during refactoring.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: MichaelBuessemeyer
PR: #8221
File: CHANGELOG.unreleased.md:14-14
Timestamp: 2024-11-25T14:52:23.201Z
Learning: For the webknossos project, changelog entries in CHANGELOG.unreleased.md should be concise and avoid unnecessary detailed explanations.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/reducers/skeletontracing_reducer_helpers.ts:125-125
Timestamp: 2024-11-22T17:17:39.914Z
Learning: In the createNode function within skeletontracing_reducer_helpers.ts, the property resolution is intentionally kept even when the parameter is renamed to mag.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: frcroth
PR: #8598
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/models/datasource/DatasetLayerAttachments.scala:89-95
Timestamp: 2025-06-02T09:49:51.047Z
Learning: In WebKnossos dataset layer attachments, multiple file types can safely use the same directory name (like "agglomerates") because the scanning logic filters by file extension. For example, AgglomerateFileInfo scans for .hdf5 files while CumsumFileInfo scans for .json files in the same "agglomerates" directory without interference.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/volumetracing_saga.tsx:433-434
Timestamp: 2024-11-22T17:19:07.947Z
Learning: In the codebase, certain usages of segmentationLayer.resolutions are intentionally retained and should not be changed to segmentationLayer.mags during refactoring.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: philippotto
PR: #8542
File: frontend/javascripts/viewer/model/sagas/volumetracing_saga.tsx:0-0
Timestamp: 2025-05-30T12:36:09.930Z
Learning: The WebKnossos frontend follows Redux immutability principles where reducers act immutably and create new state objects when changes occur. This makes reference equality checks (like prevVolumeTracing.segments !== volumeTracing.segments) reliable and efficient for detecting actual state changes, allowing memoization to work correctly.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/NeuroglancerPrecomputedMeshFileService.scala:161-166
Timestamp: 2025-04-28T14:18:04.368Z
Learning: In Scala for-comprehensions with the Fox error handling monad, Fox.fromBool() expressions should use the <- binding operator instead of the = assignment operator to properly propagate error conditions. Using = will cause validation failures to be silently ignored.

Learnt from: MichaelBuessemeyer
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/datareaders/precomputed/NeuroglancerPrecomputedShardingUtils.scala:23-28
Timestamp: 2025-04-25T11:06:13.275Z
Learning: AlfuCache in the WebKnossos codebase has default configured TTL (time-to-live) and size limits, providing automatic protection against unbounded memory growth.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/reducers/skeletontracing_reducer_helpers.ts:125-125
Timestamp: 2024-11-22T17:17:39.914Z
Learning: In the createNode function within skeletontracing_reducer_helpers.ts, the property resolution is intentionally kept even when the parameter is renamed to mag.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/volumetracing_saga.tsx:433-434
Timestamp: 2024-11-22T17:19:07.947Z
Learning: In the codebase, certain usages of segmentationLayer.resolutions are intentionally retained and should not be changed to segmentationLayer.mags during refactoring.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8202
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/DatasetErrorLoggingService.scala:68-72
Timestamp: 2024-11-25T10:02:03.702Z
Learning: In DatasetErrorLoggingService.scala, prefer using TextUtils.stackTraceAsString(exception) when logging exceptions instead of passing the exception directly to logger.error.

Learnt from: MichaelBuessemeyer
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/datareaders/precomputed/NeuroglancerPrecomputedShardingUtils.scala:23-28
Timestamp: 2025-04-25T11:06:13.275Z
Learning: AlfuCache in the WebKnossos codebase has default configured TTL (time-to-live) and size limits, providing automatic protection against unbounded memory growth.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: philippotto
PR: #8602
File: frontend/javascripts/oxalis/model/volumetracing/volume_annotation_sampling.ts:365-366
Timestamp: 2025-05-07T06:17:32.810Z
Learning: The parameter in applyVoxelMap was renamed from sliceCount to sliceOffset to better reflect its purpose, but this doesn't affect existing call sites since JavaScript/TypeScript function calls are position-based.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts:568-585
Timestamp: 2024-11-22T17:18:43.411Z
Learning: In the file frontend/javascripts/oxalis/geometries/materials/plane_material_factory.ts, the uniform name allResolutions should remain unchanged to maintain consistency with the shader code.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/NeuroglancerPrecomputedMeshFileService.scala:161-166
Timestamp: 2025-04-28T14:18:04.368Z
Learning: In Scala for-comprehensions with the Fox error handling monad, Fox.fromBool() expressions should use the <- binding operator instead of the = assignment operator to properly propagate error conditions. Using = will cause validation failures to be silently ignored.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8202
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/DatasetErrorLoggingService.scala:68-72
Timestamp: 2024-11-25T10:02:03.702Z
Learning: In DatasetErrorLoggingService.scala, prefer using TextUtils.stackTraceAsString(exception) when logging exceptions instead of passing the exception directly to logger.error.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/volumetracing_saga.tsx:433-434
Timestamp: 2024-11-22T17:19:07.947Z
Learning: In the codebase, certain usages of segmentationLayer.resolutions are intentionally retained and should not be changed to segmentationLayer.mags during refactoring.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/sagas/proofread_saga.ts:1039-1039
Timestamp: 2024-11-22T17:18:04.217Z
Learning: In frontend/javascripts/oxalis/model/sagas/proofread_saga.ts, when calling getMagInfo, the use of volumeTracingLayer.resolutions is intentional and should not be changed to volumeTracingLayer.mags.

Learnt from: dieknolle3333
PR: #8168
File: frontend/javascripts/oxalis/model/reducers/skeletontracing_reducer_helpers.ts:125-125
Timestamp: 2024-11-22T17:17:39.914Z
Learning: In the createNode function within skeletontracing_reducer_helpers.ts, the property resolution is intentionally kept even when the parameter is renamed to mag.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8598
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/models/datasource/DatasetLayerAttachments.scala:89-95
Timestamp: 2025-06-02T09:49:51.047Z
Learning: In WebKnossos dataset layer attachments, multiple file types can safely use the same directory name (like "agglomerates") because the scanning logic filters by file extension. For example, AgglomerateFileInfo scans for .hdf5 files while CumsumFileInfo scans for .json files in the same "agglomerates" directory without interference.

Learnt from: frcroth
PR: #8609
File: conf/evolutions/133-datasource-properties-in-db.sql:8-16
Timestamp: 2025-05-12T14:15:05.259Z
Learning: The database schema in WEBKNOSSOS has separate tables for dataset layers (dataset_layers) and magnifications (dataset_mags). The dataFormat field is stored in the layers table while magnification-specific fields like cubeLength (specific to WKW format) are stored in the mags table.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

Learnt from: MichaelBuessemeyer
PR: #8325
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/image/ImageCreator.scala:0-0
Timestamp: 2025-02-24T08:22:51.814Z
Learning: In ImageCreator.scala, precision loss during uint64 to double conversion is acceptable because the values are only used for image generation where each color component is ultimately represented as a single byte in ARGB format. For grayscale values (except uint24 which represents RGB), each color only uses 8 bits anyway.

Learnt from: dieknolle3333
PR: #8229
File: frontend/javascripts/oxalis/model/accessors/dataset_accessor.ts:348-354
Timestamp: 2024-11-25T14:38:49.345Z
Learning: For the getDatasetExtentAsProduct function in dataset_accessor.ts, input validation for negative or zero dimensions is not necessary.

Learnt from: frcroth
PR: #8609
File: app/models/dataset/Dataset.scala:753-775
Timestamp: 2025-05-12T13:07:29.637Z
Learning: In the updateMags method of DatasetMagsDAO (Scala), the code handles different dataset types distinctly:

1. Non-WKW datasets have magsOpt populated and use the first branch which includes axisOrder, channelIndex, and credentialId.
2. WKW datasets will have wkwResolutionsOpt populated and use the second branch which includes cubeLength.
3. The final branch is a fallback for legacy data.
   This ensures appropriate fields are populated for each dataset type.

Learnt from: frcroth
PR: #8236
File: webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala:170-173
Timestamp: 2025-04-23T08:51:57.756Z
Learning: In the webknossos codebase, classes extending FoxImplicits have access to an implicit conversion from Option[A] to Fox[A], where None is converted to an empty Fox that fails gracefully in for-comprehensions.

Learnt from: MichaelBuessemeyer
PR: #8352
File: app/models/organization/CreditTransactionService.scala:0-0
Timestamp: 2025-01-27T12:06:42.865Z
Learning: In Scala's for-comprehension with Fox (Future-like type), the <- operator ensures sequential execution. If any step fails, the entire chain short-circuits and returns early, preventing subsequent operations from executing. This makes it safe to perform validation checks before database operations.

webknossos-datastore/app/com/scalableminds/webknossos/datastore/controllers/LegacyController.scala (1)

• histogram (332-347)

frontend/javascripts/admin/rest_api.ts (1)

• getHistogramForLayer (1424-1435)

frontend/javascripts/admin/rest_api.ts (1)

• deleteDatasetOnDisk (1347-1357)

frontend/javascripts/admin/rest_api.ts (1)

• createDatasetComposition (1104-1122)

app/models/job/Job.scala (2)

• datasetName (53-53)
• datasetId (55-55)

frontend/javascripts/viewer/api/wk_dev.ts (1)

• api (74-80)

webknossos-datastore/app/com/scalableminds/webknossos/datastore/controllers/DataSourceController.scala (1)

• invalidateCache (685-690)

app/models/job/Job.scala (1)

• datasetId (55-55)

frontend/javascripts/types/api_types.ts (1)

• APIDataset (242-245)

frontend/javascripts/admin/rest_api.ts (1)

• updateDatasetDatasource (984-995)

app/models/job/Job.scala (1)

• datasetId (55-55)

webknossos-datastore/app/com/scalableminds/webknossos/datastore/rpc/RPCRequest.scala (3)

• addQueryString (28-31)
• silent (64-67)
• getWithJsonResponse (100-103)

webknossos-datastore/app/com/scalableminds/webknossos/datastore/rpc/RPCRequest.scala (2)

• addQueryString (28-31)
• postJsonWithBytesResponse (152-156)

app/controllers/UserTokenController.scala (1)

• RpcTokenHolder (30-38)

webknossos-tracingstore/app/com/scalableminds/webknossos/tracingstore/TSRemoteDatastoreClient.scala (1)

• hasSegmentIndexFile (111-117)

util/src/main/scala/com/scalableminds/util/cache/AlfuCache.scala (3)

• AlfuCache (15-42)
• AlfuCache (44-78)
• getOrLoad (17-27)

webknossos-tracingstore/app/com/scalableminds/webknossos/tracingstore/TSRemoteWebknossosClient.scala (2)

• getDatasetIdForAnnotation (77-88)
• getDataStoreUriForDataSource (71-77)

util/src/main/scala/com/scalableminds/util/tools/Fox.scala (3)

• s (229-233)
• s (233-243)
• toFox (14-14)

webknossos-datastore/app/com/scalableminds/webknossos/datastore/rpc/RPCRequest.scala (2)

• withTokenFromContext (33-36)
• getWithJsonResponse (100-103)

app/models/dataset/WKRemoteDataStoreClient.scala (1)

• hasSegmentIndexFile (80-90)

util/src/main/scala/com/scalableminds/util/objectid/ObjectId.scala (1)

• toString (12-12)

util/src/main/scala/com/scalableminds/util/tools/Fox.scala (3)

• Fox (30-223)
• Fox (225-289)
• runOptional (159-169)

webknossos-tracingstore/app/com/scalableminds/webknossos/tracingstore/tracings/RemoteFallbackLayer.scala (3)

• RemoteFallbackLayer (18-18)
• RemoteFallbackLayer (20-25)
• fromDataLayerAndDatasetId (21-24)

app/models/job/Job.scala (1)

• datasetId (55-55)

webknossos-datastore/app/com/scalableminds/webknossos/datastore/services/mesh/MeshFileService.scala (2)

• MeshChunkDataRequestList (41-44)
• MeshChunkDataRequestList (50-52)

frontend/javascripts/admin/api/token.ts (1)

• doWithToken (39-74)

[style] ~104-~104: For conciseness, consider replacing this expression with an adverb.
Context: ...ynonymously for mags throughout the UI. At the moment, WebKnossos guarantees correct renderin...

(AT_THE_MOMENT)

125-125: Unordered list style
Expected: dash; Actual: plus

(MD004, ul-style)

126-126: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

127-127: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)